Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b3341a5e693262efcfd390b26afdceda4c650e15592b919d14dfb16711359c9

Tx prefix hash: b20e5408feb57185536e732c7e6a68c1e6c3ae0845cd4d48431833e0e642adc7
Tx public key: fd686020613e32edd4ecf3eef76d521c6d2136bc17f610daf3b0a954cf0fa61c
Timestamp: 1737685321 Timestamp [UCT]: 2025-01-24 02:22:01 Age [y:d:h:m:s]: 00:144:17:47:29
Block: 1203977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103200 RingCT/type: yes/0
Extra: 01fd686020613e32edd4ecf3eef76d521c6d2136bc17f610daf3b0a954cf0fa61c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faab285e47ba73e4c7ecf475fc48bbe030a97235ffe96e1f53e525dcd624a25b 0.600000000000 1690658 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": 1203987, "vin": [ { "gen": { "height": 1203977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faab285e47ba73e4c7ecf475fc48bbe030a97235ffe96e1f53e525dcd624a25b" } } ], "extra": [ 1, 253, 104, 96, 32, 97, 62, 50, 237, 212, 236, 243, 238, 247, 109, 82, 28, 109, 33, 54, 188, 23, 246, 16, 218, 243, 176, 169, 84, 207, 15, 166, 28, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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