Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ecf54c4bbdca20ac7ba1badef517a90e7ef5a34f4d68904bbabb951507c9a5

Tx prefix hash: 24cb49f3110f1d3e4a72ec46663a1a634faab2c682c98b9db97fea56d4cbf7ee
Tx public key: 536b4ae3a262fc937a192cc3bc51f1f7db2b8248c0b099cf090bad45d1aca0b3
Timestamp: 1587896599 Timestamp [UCT]: 2020-04-26 10:23:19 Age [y:d:h:m:s]: 05:188:15:25:56
Block: 96618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1304999 RingCT/type: yes/0
Extra: 01536b4ae3a262fc937a192cc3bc51f1f7db2b8248c0b099cf090bad45d1aca0b30211000002e860e3cc90000000000000000000

1 output(s) for total of 293.673814872000 dcy

stealth address amount amount idx
00: 3b7078665bf4c94fd4f02d99d0b9d80911ac086bb138ce90b1c0e3748e47f0de 293.673814872000 171277 of 0

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": 96628, "vin": [ { "gen": { "height": 96618 } } ], "vout": [ { "amount": 293673814872, "target": { "key": "3b7078665bf4c94fd4f02d99d0b9d80911ac086bb138ce90b1c0e3748e47f0de" } } ], "extra": [ 1, 83, 107, 74, 227, 162, 98, 252, 147, 122, 25, 44, 195, 188, 81, 241, 247, 219, 43, 130, 72, 192, 176, 153, 207, 9, 11, 173, 69, 209, 172, 160, 179, 2, 17, 0, 0, 2, 232, 96, 227, 204, 144, 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