Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 934f01d8172432791690d622afc08f31e26d87b0938289fbb48e2f3e720d3773

Tx prefix hash: eda81ba862276cfa4ab03e08fc3f56c5e9576d9ea9dfc95e5c187fd0f23b9d3e
Tx public key: f0762b6ca340763ca0e6d4d88b8edc91d17373f1049f10c81acd00cf5be50683
Timestamp: 1762732468 Timestamp [UCT]: 2025-11-09 23:54:28 Age [y:d:h:m:s]: 00:059:19:47:17
Block: 1408709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42841 RingCT/type: yes/0
Extra: 01f0762b6ca340763ca0e6d4d88b8edc91d17373f1049f10c81acd00cf5be50683021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0e2e2287adb56cccbe31bec28ec5128e23f4f6be37bcf53cff7a0dc4b7ca815 0.600000000000 1897140 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": 1408719, "vin": [ { "gen": { "height": 1408709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0e2e2287adb56cccbe31bec28ec5128e23f4f6be37bcf53cff7a0dc4b7ca815" } } ], "extra": [ 1, 240, 118, 43, 108, 163, 64, 118, 60, 160, 230, 212, 216, 139, 142, 220, 145, 209, 115, 115, 241, 4, 159, 16, 200, 26, 205, 0, 207, 91, 229, 6, 131, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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