Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5df91cd1e8a65aef2e29005ca82c871ae98133cb4b80a4a85c0c46fc310c8c9

Tx prefix hash: 06cbf834877aebced080b981dd0534bc25ec9531406ac9e6ff61813690a68c59
Tx public key: e2408ae195e57a5a29383df03a0e4310675d563dfdc75b43e49911083c8cb462
Timestamp: 1762265675 Timestamp [UCT]: 2025-11-04 14:14:35 Age [y:d:h:m:s]: 00:053:18:08:20
Block: 1404841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38489 RingCT/type: yes/0
Extra: 01e2408ae195e57a5a29383df03a0e4310675d563dfdc75b43e49911083c8cb46202110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2dd89d7a55a3bf529f0527be4d3fc041c68c6001dee371e5a9ab1d4303b864e 0.600000000000 1893208 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": 1404851, "vin": [ { "gen": { "height": 1404841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2dd89d7a55a3bf529f0527be4d3fc041c68c6001dee371e5a9ab1d4303b864e" } } ], "extra": [ 1, 226, 64, 138, 225, 149, 229, 122, 90, 41, 56, 61, 240, 58, 14, 67, 16, 103, 93, 86, 61, 253, 199, 91, 67, 228, 153, 17, 8, 60, 140, 180, 98, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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