Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39162e7bdd28440231f6e36abfb01d5921350f6aa71dc1012c3d00288550bda4

Tx prefix hash: c83c8d008ea556de47072e1a8a011dbbe313fe4306a6b6305fbe3c836c4e5dd1
Tx public key: 7b5d9c526321a91ed53f980e14777d692145ce937bb6041ff2a38b6c7d1069a2
Timestamp: 1737017658 Timestamp [UCT]: 2025-01-16 08:54:18 Age [y:d:h:m:s]: 00:156:18:02:23
Block: 1198489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111667 RingCT/type: yes/0
Extra: 017b5d9c526321a91ed53f980e14777d692145ce937bb6041ff2a38b6c7d1069a2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566ba641a33e9d3cda53f45592bb50ec6f8057000ac9c2de4e90e04ea3a1b087 0.600000000000 1685114 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": 1198499, "vin": [ { "gen": { "height": 1198489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566ba641a33e9d3cda53f45592bb50ec6f8057000ac9c2de4e90e04ea3a1b087" } } ], "extra": [ 1, 123, 93, 156, 82, 99, 33, 169, 30, 213, 63, 152, 14, 20, 119, 125, 105, 33, 69, 206, 147, 123, 182, 4, 31, 242, 163, 139, 108, 125, 16, 105, 162, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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