Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bce02f31da96615b1868930850d4dbc8deacad997a37cd28de4ae4c5621132b8

Tx prefix hash: 1ef475d4a399ce5026c0048f969643d834078e11e29980eefc95cf693bfe9a81
Tx public key: 6deefb9fea0e61e86c147c2fadc21f1848e852f936694f8f48756a59a445c628
Timestamp: 1732546389 Timestamp [UCT]: 2024-11-25 14:53:09 Age [y:d:h:m:s]: 00:341:05:48:53
Block: 1161473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241412 RingCT/type: yes/0
Extra: 016deefb9fea0e61e86c147c2fadc21f1848e852f936694f8f48756a59a445c62802110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5ab21ad924d6515c1e573794712ac081fa1392db8bcc69bb52ae15143b17aee 0.600000000000 1647128 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": 1161483, "vin": [ { "gen": { "height": 1161473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5ab21ad924d6515c1e573794712ac081fa1392db8bcc69bb52ae15143b17aee" } } ], "extra": [ 1, 109, 238, 251, 159, 234, 14, 97, 232, 108, 20, 124, 47, 173, 194, 31, 24, 72, 232, 82, 249, 54, 105, 79, 143, 72, 117, 106, 89, 164, 69, 198, 40, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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