Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cce92b86410272c7859f3c6835e1b9b65d0df7e2d442b9ec4dd0f9824b04814

Tx prefix hash: 8269456630dc140f68d1fd506dc294c61c413826a87960921192204e4316bcc9
Tx public key: 59c0e104af99c822be96f78b4795d339c3db3bcd69ef0dbb11179f55e731d348
Timestamp: 1737203734 Timestamp [UCT]: 2025-01-18 12:35:34 Age [y:d:h:m:s]: 00:057:05:44:28
Block: 1200051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40671 RingCT/type: yes/0
Extra: 0159c0e104af99c822be96f78b4795d339c3db3bcd69ef0dbb11179f55e731d348021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f50dbf0b5446a267b3f200bbd673fb036a55574a84718d68b9da74be2ec2da7 0.600000000000 1686692 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": 1200061, "vin": [ { "gen": { "height": 1200051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f50dbf0b5446a267b3f200bbd673fb036a55574a84718d68b9da74be2ec2da7" } } ], "extra": [ 1, 89, 192, 225, 4, 175, 153, 200, 34, 190, 150, 247, 139, 71, 149, 211, 57, 195, 219, 59, 205, 105, 239, 13, 187, 17, 23, 159, 85, 231, 49, 211, 72, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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