Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7070cb14b4e98d88fdcb803910a3c68a095c6df7dcbf471fc802c8bd3e85723

Tx prefix hash: 6d41c41a798461c849d318371f2d070afd898c6a1d624421028925e632dff2b1
Tx public key: c85e7fdab2a9adfca91374eba2b97d95eff913203fd912ddb93989a143e31972
Timestamp: 1721217919 Timestamp [UCT]: 2024-07-17 12:05:19 Age [y:d:h:m:s]: 00:219:23:54:46
Block: 1067670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157093 RingCT/type: yes/0
Extra: 01c85e7fdab2a9adfca91374eba2b97d95eff913203fd912ddb93989a143e3197202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ccd178a13a7fb25c75c7eafb474164995d1f7c5b637f5f13f613ad840c3494d 0.600000000000 1538541 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": 1067680, "vin": [ { "gen": { "height": 1067670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ccd178a13a7fb25c75c7eafb474164995d1f7c5b637f5f13f613ad840c3494d" } } ], "extra": [ 1, 200, 94, 127, 218, 178, 169, 173, 252, 169, 19, 116, 235, 162, 185, 125, 149, 239, 249, 19, 32, 63, 217, 18, 221, 185, 57, 137, 161, 67, 227, 25, 114, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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