Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d638f25e088a036bf9bd304e77ece8d0f39cb75cd76f9346e51063f89c8af0

Tx prefix hash: daf643917230d57670715f605d4777a8e6e7346349cbaa713979a08d56d00eff
Tx public key: 9cff3eb421f12a3292010c49da7a0d6ce752692184244a5154231e65afc5ccc5
Timestamp: 1709033483 Timestamp [UCT]: 2024-02-27 11:31:23 Age [y:d:h:m:s]: 01:017:04:22:01
Block: 966644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273296 RingCT/type: yes/0
Extra: 019cff3eb421f12a3292010c49da7a0d6ce752692184244a5154231e65afc5ccc50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da9fd23b9b9715218354b6a79ecc7a889a9b85cc9b4bf35009e9ccb59046b4bf 0.600000000000 1426411 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": 966654, "vin": [ { "gen": { "height": 966644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da9fd23b9b9715218354b6a79ecc7a889a9b85cc9b4bf35009e9ccb59046b4bf" } } ], "extra": [ 1, 156, 255, 62, 180, 33, 241, 42, 50, 146, 1, 12, 73, 218, 122, 13, 108, 231, 82, 105, 33, 132, 36, 74, 81, 84, 35, 30, 101, 175, 197, 204, 197, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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