Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1106d6d5df03e346d5f63c03fb0cf0a98f265acc558390461b369a9c0b7d132e

Tx prefix hash: c724eb825338a9b1de0d233c77c849b8da2280f7348c393bfc289f3117a07923
Tx public key: 20abc79d168d54ac68ef7be10f95c2d230b958de6dc50fc1d580f8e3e8942413
Timestamp: 1708143619 Timestamp [UCT]: 2024-02-17 04:20:19 Age [y:d:h:m:s]: 01:029:07:53:50
Block: 959256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282008 RingCT/type: yes/0
Extra: 0120abc79d168d54ac68ef7be10f95c2d230b958de6dc50fc1d580f8e3e89424130211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c52030619633abe39f547a2fdb2e7e7cb7efa7bfaf5c28530d9d62a75b552d84 0.600000000000 1418787 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": 959266, "vin": [ { "gen": { "height": 959256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c52030619633abe39f547a2fdb2e7e7cb7efa7bfaf5c28530d9d62a75b552d84" } } ], "extra": [ 1, 32, 171, 199, 157, 22, 141, 84, 172, 104, 239, 123, 225, 15, 149, 194, 210, 48, 185, 88, 222, 109, 197, 15, 193, 213, 128, 248, 227, 232, 148, 36, 19, 2, 17, 0, 0, 0, 5, 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