Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74ed0326b4c64fa7a830c5638ba6e5399bd8bbd40f8d15901de14c53ee6ffb78

Tx prefix hash: 3e2cea136a93f3422d8532d54346c15fdd0617287babdb448eb9d80d9ef88a64
Tx public key: b149959860f39ef735ed7bd3e384a5e27d10401edbe8f5aacb6a36bbb9fc6d45
Timestamp: 1735349530 Timestamp [UCT]: 2024-12-28 01:32:10 Age [y:d:h:m:s]: 00:081:20:38:27
Block: 1184673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58322 RingCT/type: yes/0
Extra: 01b149959860f39ef735ed7bd3e384a5e27d10401edbe8f5aacb6a36bbb9fc6d450211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6e739b421301014d8f164f0c75833fb186df5c88d4e3d683e0ed9c6e140f4e1 0.600000000000 1671132 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": 1184683, "vin": [ { "gen": { "height": 1184673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6e739b421301014d8f164f0c75833fb186df5c88d4e3d683e0ed9c6e140f4e1" } } ], "extra": [ 1, 177, 73, 149, 152, 96, 243, 158, 247, 53, 237, 123, 211, 227, 132, 165, 226, 125, 16, 64, 30, 219, 232, 245, 170, 203, 106, 54, 187, 185, 252, 109, 69, 2, 17, 0, 0, 0, 3, 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