Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d2dc642ca28c3917f756eb90b5e4c5cba3d9acd9973bfae440f934fa7e9b518

Tx prefix hash: 5a352633f1dc27b4b02dd4d06ad4d77e90a6edc03033429eb8688d26e6899ebb
Tx public key: 20ea15e2bd1ad256ddd442b30802723d6ef3cf522200161195d48f19aa6d7197
Timestamp: 1574493294 Timestamp [UCT]: 2019-11-23 07:14:54 Age [y:d:h:m:s]: 05:343:12:48:03
Block: 15204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1386237 RingCT/type: yes/0
Extra: 0120ea15e2bd1ad256ddd442b30802723d6ef3cf522200161195d48f19aa6d7197021100000002f95225a5000000000000000000

1 output(s) for total of 546.542224848000 dcy

stealth address amount amount idx
00: 838cb05d015a17d13dad70be144f0a6e05f2fd52733000a1087ce2a0c066115d 546.542224848000 20160 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": 15214, "vin": [ { "gen": { "height": 15204 } } ], "vout": [ { "amount": 546542224848, "target": { "key": "838cb05d015a17d13dad70be144f0a6e05f2fd52733000a1087ce2a0c066115d" } } ], "extra": [ 1, 32, 234, 21, 226, 189, 26, 210, 86, 221, 212, 66, 179, 8, 2, 114, 61, 110, 243, 207, 82, 34, 0, 22, 17, 149, 212, 143, 25, 170, 109, 113, 151, 2, 17, 0, 0, 0, 2, 249, 82, 37, 165, 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