Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b38f528791638e07586af551dc0605c1e220329b449bbbc5c2ca64bdb3a097f

Tx prefix hash: 2417ed00ab0d4533a84a60621b52bbaeda002f31879bd5a6769ced2803399fe0
Tx public key: dea54c8af3a5a3f9c924f6aff44f28340b0229b2d176a6eeebc9d4e69001088f
Timestamp: 1723877589 Timestamp [UCT]: 2024-08-17 06:53:09 Age [y:d:h:m:s]: 01:082:15:29:21
Block: 1089710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317523 RingCT/type: yes/0
Extra: 01dea54c8af3a5a3f9c924f6aff44f28340b0229b2d176a6eeebc9d4e69001088f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67b0b89671e07761fa5954ff4f6ed950b27e4e0f3c4ef1a8129d092d8b65dd34 0.600000000000 1564333 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": 1089720, "vin": [ { "gen": { "height": 1089710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67b0b89671e07761fa5954ff4f6ed950b27e4e0f3c4ef1a8129d092d8b65dd34" } } ], "extra": [ 1, 222, 165, 76, 138, 243, 165, 163, 249, 201, 36, 246, 175, 244, 79, 40, 52, 11, 2, 41, 178, 209, 118, 166, 238, 235, 201, 212, 230, 144, 1, 8, 143, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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