Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 184975bcca6c1a711b02c6d1c8d096d630e61640efa37f6f18164c165ef634de

Tx prefix hash: b59e3832d92b224c8ea56a05790047de09011dfc37f9f2520184225c1ac16a2e
Tx public key: 3071a00f7b009fccae8b7d64e53cb72f4040c4caaf54b8fd7f619e2c438ed597
Timestamp: 1745530457 Timestamp [UCT]: 2025-04-24 21:34:17 Age [y:d:h:m:s]: 00:013:02:36:41
Block: 1268700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9380 RingCT/type: yes/0
Extra: 013071a00f7b009fccae8b7d64e53cb72f4040c4caaf54b8fd7f619e2c438ed5970211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f49a87238ca7160933d657cefcb5dc5e6182e3eb48f23fa12f61b0da18763ac 0.600000000000 1755931 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": 1268710, "vin": [ { "gen": { "height": 1268700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f49a87238ca7160933d657cefcb5dc5e6182e3eb48f23fa12f61b0da18763ac" } } ], "extra": [ 1, 48, 113, 160, 15, 123, 0, 159, 204, 174, 139, 125, 100, 229, 60, 183, 47, 64, 64, 196, 202, 175, 84, 184, 253, 127, 97, 158, 44, 67, 142, 213, 151, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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