Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac2d40dc7a7ea14c2f4af3987ac431cba86b389c7552ea02b9a88c0bee0ee295

Tx prefix hash: b50eae24dbd256d2c8badcda7e0b3d468f7d1e28c959974d52d751d95c864b33
Tx public key: 2712f533f8a8a518fbb7e8510d95885d890545da309a5551a9ab6e347aeafe3a
Timestamp: 1714161721 Timestamp [UCT]: 2024-04-26 20:02:01 Age [y:d:h:m:s]: 01:028:22:55:17
Block: 1009147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281660 RingCT/type: yes/0
Extra: 012712f533f8a8a518fbb7e8510d95885d890545da309a5551a9ab6e347aeafe3a02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6147e38c535a7a559d64bf2c92f75184a106801c3259a1c5bcd1461d7d703faf 0.600000000000 1470737 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": 1009157, "vin": [ { "gen": { "height": 1009147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6147e38c535a7a559d64bf2c92f75184a106801c3259a1c5bcd1461d7d703faf" } } ], "extra": [ 1, 39, 18, 245, 51, 248, 168, 165, 24, 251, 183, 232, 81, 13, 149, 136, 93, 137, 5, 69, 218, 48, 154, 85, 81, 169, 171, 110, 52, 122, 234, 254, 58, 2, 17, 0, 0, 0, 9, 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