Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7c0b6a4e0d3cd63cef58442f9e2f0367ae078bf2ca04a499ad7dfc838aa570a6

Tx prefix hash: 833d2b32a46588b69a4adb92b22a3121c8f2339e9a8c69d698096aa403a47659
Tx public key: d497753a74fe8c25adbe8596c9133d53ba1c872ee5e2a4f6f0ec7f45942d1321
Timestamp: 1711856796 Timestamp [UCT]: 2024-03-31 03:46:36 Age [y:d:h:m:s]: 01:025:09:41:04
Block: 990069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279104 RingCT/type: yes/0
Extra: 01d497753a74fe8c25adbe8596c9133d53ba1c872ee5e2a4f6f0ec7f45942d13210211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30134119e6c7cde59fe4d7a8ddb69da39c1a1fae04c0206f424bf2df069b352a 0.600000000000 1450389 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 990079, "vin": [ { "gen": { "height": 990069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30134119e6c7cde59fe4d7a8ddb69da39c1a1fae04c0206f424bf2df069b352a" } } ], "extra": [ 1, 212, 151, 117, 58, 116, 254, 140, 37, 173, 190, 133, 150, 201, 19, 61, 83, 186, 28, 135, 46, 229, 226, 164, 246, 240, 236, 127, 69, 148, 45, 19, 33, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8