Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7103bf61bf4f148eb5e8b11ed3514c6f73f00dc6aa15ca4120c404fbc7cf557c

Tx prefix hash: 45715afa3cdebdf5f398bec78f7d80d440e6d0c1083c7868031f34e4b2524871
Tx public key: 4503c3c836fca06e41da86aac9dfa783ef23389a7c4d8e935d1dc4efe50fc4be
Timestamp: 1735497965 Timestamp [UCT]: 2024-12-29 18:46:05 Age [y:d:h:m:s]: 00:099:03:05:36
Block: 1185903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70631 RingCT/type: yes/0
Extra: 014503c3c836fca06e41da86aac9dfa783ef23389a7c4d8e935d1dc4efe50fc4be0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8740e1aa566dce13bd028afba494c27be8f0f8e9bc0b33ab54212ed4318dbc01 0.600000000000 1672378 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": 1185913, "vin": [ { "gen": { "height": 1185903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8740e1aa566dce13bd028afba494c27be8f0f8e9bc0b33ab54212ed4318dbc01" } } ], "extra": [ 1, 69, 3, 195, 200, 54, 252, 160, 110, 65, 218, 134, 170, 201, 223, 167, 131, 239, 35, 56, 154, 124, 77, 142, 147, 93, 29, 196, 239, 229, 15, 196, 190, 2, 17, 0, 0, 0, 5, 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