Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 217725d2f2b3d98968abbe30cc6a31db785c413bfd3937e1ec9438ae3c162960

Tx prefix hash: c6053e0532b2741f6caca109b2baf82f5874f888b6373f69e93f17ee01edc0c8
Tx public key: 36fd6cabcca97dbf60db7a32cb50fb12477db4d2c5b51ba53c8aa63f499462db
Timestamp: 1723738262 Timestamp [UCT]: 2024-08-15 16:11:02 Age [y:d:h:m:s]: 01:165:22:54:13
Block: 1088546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377002 RingCT/type: yes/0
Extra: 0136fd6cabcca97dbf60db7a32cb50fb12477db4d2c5b51ba53c8aa63f499462db021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13fcec7c679f2d7714e7648cb76646a49174a031adf450b1ea5fae5446fdaac7 0.600000000000 1563163 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": 1088556, "vin": [ { "gen": { "height": 1088546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13fcec7c679f2d7714e7648cb76646a49174a031adf450b1ea5fae5446fdaac7" } } ], "extra": [ 1, 54, 253, 108, 171, 204, 169, 125, 191, 96, 219, 122, 50, 203, 80, 251, 18, 71, 125, 180, 210, 197, 181, 27, 165, 60, 138, 166, 63, 73, 148, 98, 219, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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