Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba10fdd74b9d0810671a33dd877a59c185e0184b46c76028a55a46ff4439275f

Tx prefix hash: 063c25b949228e67618606037992e5c8948f0e651a5a410f29e88ba735b6df68
Tx public key: 7057cdc28b2b2c9d90d1678afd85f01a314c54a5ecef922346ead725c8eac2af
Timestamp: 1732249620 Timestamp [UCT]: 2024-11-22 04:27:00 Age [y:d:h:m:s]: 00:002:03:48:39
Block: 1159007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1552 RingCT/type: yes/0
Extra: 017057cdc28b2b2c9d90d1678afd85f01a314c54a5ecef922346ead725c8eac2af021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb207a24b0fbbad099e15c332459c26270e0b0d8f5bfd2f08aa7add61f42bccf 0.600000000000 1644638 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": 1159017, "vin": [ { "gen": { "height": 1159007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb207a24b0fbbad099e15c332459c26270e0b0d8f5bfd2f08aa7add61f42bccf" } } ], "extra": [ 1, 112, 87, 205, 194, 139, 43, 44, 157, 144, 209, 103, 138, 253, 133, 240, 26, 49, 76, 84, 165, 236, 239, 146, 35, 70, 234, 215, 37, 200, 234, 194, 175, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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