Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cc175268440f300792be8d14c216c0bd24ecd5579ddc2aaaaf91646fba5add5

Tx prefix hash: f93a8f982406c6dc05f35528b2ad6a76b63874adf727f1baea596d90df016595
Tx public key: 7ec258c8fa6b2fb8fa5d3dd785a192288ce60f56c99e1fa270ad92445c5e0ba4
Timestamp: 1721847485 Timestamp [UCT]: 2024-07-24 18:58:05 Age [y:d:h:m:s]: 00:280:15:37:43
Block: 1072867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200504 RingCT/type: yes/0
Extra: 017ec258c8fa6b2fb8fa5d3dd785a192288ce60f56c99e1fa270ad92445c5e0ba402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f6d9bac6e07e8a9807d048ab84f876d9cf8beb0767767db27541855dcade23 0.600000000000 1545364 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": 1072877, "vin": [ { "gen": { "height": 1072867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f6d9bac6e07e8a9807d048ab84f876d9cf8beb0767767db27541855dcade23" } } ], "extra": [ 1, 126, 194, 88, 200, 250, 107, 47, 184, 250, 93, 61, 215, 133, 161, 146, 40, 140, 230, 15, 86, 201, 158, 31, 162, 112, 173, 146, 68, 92, 94, 11, 164, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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