Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92c6449a7150886fd3a28d3c1e752dfad0f2172c0fd38449483846cff61d8652

Tx prefix hash: 9c3bacc72f2d619b3438a90a9032ff6da79a02316d91d25cf3d523875c638dff
Tx public key: 0906b7d31db6864d851801a2af1d799ce68f49fe0880c4a6fedc4a4cf4e34352
Timestamp: 1714421108 Timestamp [UCT]: 2024-04-29 20:05:08 Age [y:d:h:m:s]: 01:188:19:19:56
Block: 1011300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393571 RingCT/type: yes/0
Extra: 010906b7d31db6864d851801a2af1d799ce68f49fe0880c4a6fedc4a4cf4e3435202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d5660f8c2de061c4605b0e8316d4c855991147e58d5c9cb83e27673ed2be547 0.600000000000 1473494 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": 1011310, "vin": [ { "gen": { "height": 1011300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d5660f8c2de061c4605b0e8316d4c855991147e58d5c9cb83e27673ed2be547" } } ], "extra": [ 1, 9, 6, 183, 211, 29, 182, 134, 77, 133, 24, 1, 162, 175, 29, 121, 156, 230, 143, 73, 254, 8, 128, 196, 166, 254, 220, 74, 76, 244, 227, 67, 82, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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