Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5881d80620234733a195c2aadaa4a361a2a8d69022387fd88885ffdbd32adc23

Tx prefix hash: a7408ae624b3f6f247bb79da59ae3373834af2169cb9e3ba4962e45aefc47db8
Tx public key: d0f8955bda98c8adf857eb4e3bb274df7769155f0af1453a8847747279821c6d
Timestamp: 1697199034 Timestamp [UCT]: 2023-10-13 12:10:34 Age [y:d:h:m:s]: 01:167:02:13:05
Block: 868723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380451 RingCT/type: yes/0
Extra: 01d0f8955bda98c8adf857eb4e3bb274df7769155f0af1453a8847747279821c6d02110000000136a45730000000000000000000

1 output(s) for total of 0.812007623000 dcy

stealth address amount amount idx
00: d016c83965e9d4dd0b527b615a319b61422e25c43af6dcef685fd7e81eb3ae5f 0.812007623000 1323542 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": 868733, "vin": [ { "gen": { "height": 868723 } } ], "vout": [ { "amount": 812007623, "target": { "key": "d016c83965e9d4dd0b527b615a319b61422e25c43af6dcef685fd7e81eb3ae5f" } } ], "extra": [ 1, 208, 248, 149, 91, 218, 152, 200, 173, 248, 87, 235, 78, 59, 178, 116, 223, 119, 105, 21, 95, 10, 241, 69, 58, 136, 71, 116, 114, 121, 130, 28, 109, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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