Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd1891af20a7da37edece32718c8162abd4ee6e6458bf5d3b66bb61470945f14

Tx prefix hash: 1319cd9ea57beeb8a0383a1fdb579954ab435e66205e6e61d2afe3127772db5c
Tx public key: 0df2af7c4fd5709b538c1719585130e5d4f450402bd5dfd2b00c06387cffb637
Timestamp: 1752809494 Timestamp [UCT]: 2025-07-18 03:31:34 Age [y:d:h:m:s]: 00:171:19:11:46
Block: 1327844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121661 RingCT/type: yes/0
Extra: 010df2af7c4fd5709b538c1719585130e5d4f450402bd5dfd2b00c06387cffb637021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00b1e909f2c5438533144110e276f98a6bc4df78490fa6c692b9aab9d0233c0e 0.600000000000 1815603 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": 1327854, "vin": [ { "gen": { "height": 1327844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00b1e909f2c5438533144110e276f98a6bc4df78490fa6c692b9aab9d0233c0e" } } ], "extra": [ 1, 13, 242, 175, 124, 79, 213, 112, 155, 83, 140, 23, 25, 88, 81, 48, 229, 212, 244, 80, 64, 43, 213, 223, 210, 176, 12, 6, 56, 124, 255, 182, 55, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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