Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a726ad1be927a7dd47f6a02c88efa0f931bbe8e87d36e73234875f7aba5c9683

Tx prefix hash: fb00320a988282a949d6fbbe599f29e786c9c740a2ebb1177c7939628c948a1e
Tx public key: ae162e7b812c18cbdae32f0107aa852c6096777749e7138f4a08ebe5eab66a2c
Timestamp: 1720506300 Timestamp [UCT]: 2024-07-09 06:25:00 Age [y:d:h:m:s]: 01:114:14:55:23
Block: 1061759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340433 RingCT/type: yes/0
Extra: 01ae162e7b812c18cbdae32f0107aa852c6096777749e7138f4a08ebe5eab66a2c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 516d1cbc81dd9233aa898fed0f461e4cad9efd66ef4882c79319bbb26312a690 0.600000000000 1532254 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": 1061769, "vin": [ { "gen": { "height": 1061759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "516d1cbc81dd9233aa898fed0f461e4cad9efd66ef4882c79319bbb26312a690" } } ], "extra": [ 1, 174, 22, 46, 123, 129, 44, 24, 203, 218, 227, 47, 1, 7, 170, 133, 44, 96, 150, 119, 119, 73, 231, 19, 143, 74, 8, 235, 229, 234, 182, 106, 44, 2, 17, 0, 0, 0, 2, 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