Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcb6fe84d4edda8dac88bc45176d71575ef84d4a7e223fbd5af26bd0294f6dc2

Tx prefix hash: a35ed2c104725002fd77cd14bf6b4327ffc54c3f6b02573975a621a2f81666d8
Tx public key: fb8c91b0cf4fc3f8eb708c4c7181f7589fb760cce76d64ff432176f8970d82d9
Timestamp: 1699632775 Timestamp [UCT]: 2023-11-10 16:12:55 Age [y:d:h:m:s]: 01:138:07:08:28
Block: 888709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360009 RingCT/type: yes/0
Extra: 01fb8c91b0cf4fc3f8eb708c4c7181f7589fb760cce76d64ff432176f8970d82d902110000000233af99f4000000000000000000

1 output(s) for total of 0.697169152000 dcy

stealth address amount amount idx
00: 6c8688157f06313cd5502e3863bc1ae6efa235827182e745225df796951eb68f 0.697169152000 1344664 of 0

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": 888719, "vin": [ { "gen": { "height": 888709 } } ], "vout": [ { "amount": 697169152, "target": { "key": "6c8688157f06313cd5502e3863bc1ae6efa235827182e745225df796951eb68f" } } ], "extra": [ 1, 251, 140, 145, 176, 207, 79, 195, 248, 235, 112, 140, 76, 113, 129, 247, 88, 159, 183, 96, 204, 231, 109, 100, 255, 67, 33, 118, 248, 151, 13, 130, 217, 2, 17, 0, 0, 0, 2, 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