Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbafdeb97ba2138d25b0bdaf5e8af33dbd524f345b44c4a9d1a7418d1a5a2279

Tx prefix hash: 429cd1e79f21b2efc2229f914ff223622090fab1ee8bce0d6375d57cc6e3cd33
Tx public key: 9d1653d49bbbcabdd3f5019f989328c06c9352b997230598e252f512d66068e3
Timestamp: 1709429438 Timestamp [UCT]: 2024-03-03 01:30:38 Age [y:d:h:m:s]: 01:256:06:15:29
Block: 969923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441887 RingCT/type: yes/0
Extra: 019d1653d49bbbcabdd3f5019f989328c06c9352b997230598e252f512d66068e302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a527a8a9d9ed2f1a73867dde520a78dcc8d270e3ff70b4d26b6e61199815fdc 0.600000000000 1429772 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": 969933, "vin": [ { "gen": { "height": 969923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a527a8a9d9ed2f1a73867dde520a78dcc8d270e3ff70b4d26b6e61199815fdc" } } ], "extra": [ 1, 157, 22, 83, 212, 155, 187, 202, 189, 211, 245, 1, 159, 152, 147, 40, 192, 108, 147, 82, 185, 151, 35, 5, 152, 226, 82, 245, 18, 214, 96, 104, 227, 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