Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daad0d4abde9b7dce3126d3f75ae57e5a7708b473678ed7f70eb687e3203b0ee

Tx prefix hash: 7fea570b0582482a8225ce0a4715ffbaff329dd5adef269d13c187871d827135
Tx public key: 51a4c30b0488d03f142aec761070961e1c58419047cda6fffe6122142d4e8f5b
Timestamp: 1727602170 Timestamp [UCT]: 2024-09-29 09:29:30 Age [y:d:h:m:s]: 00:186:20:37:43
Block: 1120590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133344 RingCT/type: yes/0
Extra: 0151a4c30b0488d03f142aec761070961e1c58419047cda6fffe6122142d4e8f5b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2259db7d27b8300a8c0dd38a3a1c299c66fa10e75b72e651602468cba03aa44 0.600000000000 1602559 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": 1120600, "vin": [ { "gen": { "height": 1120590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2259db7d27b8300a8c0dd38a3a1c299c66fa10e75b72e651602468cba03aa44" } } ], "extra": [ 1, 81, 164, 195, 11, 4, 136, 208, 63, 20, 42, 236, 118, 16, 112, 150, 30, 28, 88, 65, 144, 71, 205, 166, 255, 254, 97, 34, 20, 45, 78, 143, 91, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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