Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9055c5ba0227682e50505c49152a8d5fe52696f592c2d4668939717dd2b28d1c

Tx prefix hash: 9d4eb9ef7ad5132240e235d382156adf1451b9179d59819d9cf23d26ab7651fb
Tx public key: 36bb0cebd1f603aeceac182130e97cfef9aa92c09d4ba4ae5adb9b0bad6d9ae2
Timestamp: 1727050360 Timestamp [UCT]: 2024-09-23 00:12:40 Age [y:d:h:m:s]: 00:199:22:44:27
Block: 1116008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142714 RingCT/type: yes/0
Extra: 0136bb0cebd1f603aeceac182130e97cfef9aa92c09d4ba4ae5adb9b0bad6d9ae202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f85d2eb4bd4451ef075ecc5ecc44c9f0d11f47caf821169f56730fc987d3562 0.600000000000 1596341 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": 1116018, "vin": [ { "gen": { "height": 1116008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f85d2eb4bd4451ef075ecc5ecc44c9f0d11f47caf821169f56730fc987d3562" } } ], "extra": [ 1, 54, 187, 12, 235, 209, 246, 3, 174, 206, 172, 24, 33, 48, 233, 124, 254, 249, 170, 146, 192, 157, 75, 164, 174, 90, 219, 155, 11, 173, 109, 154, 226, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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