Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd53d0abca2ab9fc5851ffa6800e9bdc018e37409e7d0bf57fae6b30f503559c

Tx prefix hash: c22a16ed2e066ab1f43c60656ac976f2a606bcf567900de21207e6faad79439f
Tx public key: cf320723858afd0c01911f4efc30b82b91922ac83c16dedd01ba1293b4d24f79
Timestamp: 1631644687 Timestamp [UCT]: 2021-09-14 18:38:07 Age [y:d:h:m:s]: 03:174:04:52:44
Block: 333790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899920 RingCT/type: yes/0
Extra: 01cf320723858afd0c01911f4efc30b82b91922ac83c16dedd01ba1293b4d24f790211000000025d7cc334000000000000000000

1 output(s) for total of 48.087822971000 dcy

stealth address amount amount idx
00: 3d877a60cb1583d3570097cc953a38d9cf69ed235c64b6b4d87a61be65f12d4e 48.087822971000 688659 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": 333800, "vin": [ { "gen": { "height": 333790 } } ], "vout": [ { "amount": 48087822971, "target": { "key": "3d877a60cb1583d3570097cc953a38d9cf69ed235c64b6b4d87a61be65f12d4e" } } ], "extra": [ 1, 207, 50, 7, 35, 133, 138, 253, 12, 1, 145, 31, 78, 252, 48, 184, 43, 145, 146, 42, 200, 60, 22, 222, 221, 1, 186, 18, 147, 180, 210, 79, 121, 2, 17, 0, 0, 0, 2, 93, 124, 195, 52, 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