Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2427e98200e5f9642245028221db90d120ea2310eccf0f78ee8548a4bc20b5a0

Tx prefix hash: d43a0336d17fbbc25c8fb2142e6b03c727030ba799bd8be56493138e7208a9eb
Tx public key: ade8589f8f801e2c2d71aecc20edce27633ea330809b37106f8d93cffdfd53f2
Timestamp: 1702596288 Timestamp [UCT]: 2023-12-14 23:24:48 Age [y:d:h:m:s]: 01:036:17:46:15
Block: 913263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287587 RingCT/type: yes/0
Extra: 01ade8589f8f801e2c2d71aecc20edce27633ea330809b37106f8d93cffdfd53f202110000000533af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40bca3e3cddb030d8070e91b9911c3f4fc64ee34b9c7d9f53d3ef034799aed38 0.600000000000 1370529 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": 913273, "vin": [ { "gen": { "height": 913263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40bca3e3cddb030d8070e91b9911c3f4fc64ee34b9c7d9f53d3ef034799aed38" } } ], "extra": [ 1, 173, 232, 88, 159, 143, 128, 30, 44, 45, 113, 174, 204, 32, 237, 206, 39, 99, 62, 163, 48, 128, 155, 55, 16, 111, 141, 147, 207, 253, 253, 83, 242, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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