Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37cad679cb94e5d3389783ad13c14742669b2da130a977b9d83e30f76364e17

Tx prefix hash: f8a6a1d211ef12e65564a17cf0d8a030d16aca72c9e8df6fa16abf1b514aae5c
Tx public key: 261ef1bb9d41335d5f75db798a3a0d0a2b42570fe65fd975f5980360b1e81b1f
Timestamp: 1711591921 Timestamp [UCT]: 2024-03-28 02:12:01 Age [y:d:h:m:s]: 00:338:12:52:33
Block: 987860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242023 RingCT/type: yes/0
Extra: 01261ef1bb9d41335d5f75db798a3a0d0a2b42570fe65fd975f5980360b1e81b1f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be89eec5d6ff5e1f1bc11a9e08a6894b5c25c0081ce691482d57017bd329c28 0.600000000000 1448121 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": 987870, "vin": [ { "gen": { "height": 987860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be89eec5d6ff5e1f1bc11a9e08a6894b5c25c0081ce691482d57017bd329c28" } } ], "extra": [ 1, 38, 30, 241, 187, 157, 65, 51, 93, 95, 117, 219, 121, 138, 58, 13, 10, 43, 66, 87, 15, 230, 95, 217, 117, 245, 152, 3, 96, 177, 232, 27, 31, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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