Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aaa9802f95d5b49c639fc3cb99bd90c07c0d0911c740e83c2e25a6b256d9c11

Tx prefix hash: d2fc0b91a956bf1ff9dce85b97b312bc20cfac9e2e84979282945e5426ad5f62
Tx public key: 46f29801cd992fd47702a3cfb2f050759cf327c4ecfac7f04efa861c359f6906
Timestamp: 1710372424 Timestamp [UCT]: 2024-03-13 23:27:04 Age [y:d:h:m:s]: 01:012:11:24:37
Block: 977760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269861 RingCT/type: yes/0
Extra: 0146f29801cd992fd47702a3cfb2f050759cf327c4ecfac7f04efa861c359f690602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bb4eab9e61629412752cb2c0e90bf2376666868af1f1662a6e3e39052fd1a5d 0.600000000000 1437767 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": 977770, "vin": [ { "gen": { "height": 977760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb4eab9e61629412752cb2c0e90bf2376666868af1f1662a6e3e39052fd1a5d" } } ], "extra": [ 1, 70, 242, 152, 1, 205, 153, 47, 212, 119, 2, 163, 207, 178, 240, 80, 117, 156, 243, 39, 196, 236, 250, 199, 240, 78, 250, 134, 28, 53, 159, 105, 6, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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