Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a40f76c8099c146546c43c33482000de11b2bc8e27b4f5bc226cd9b4f0aa0bd

Tx prefix hash: 82f1dfa392d309c2772a6ba270181542e5f28b03c68d4aefc7b5006d187e7225
Tx public key: 3001b4fa63c5adee8fb92f61ffa87e5361f61af11d4b59495cd600a7f6f0d00c
Timestamp: 1761605879 Timestamp [UCT]: 2025-10-27 22:57:59 Age [y:d:h:m:s]: 00:061:19:47:35
Block: 1399383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44258 RingCT/type: yes/0
Extra: 013001b4fa63c5adee8fb92f61ffa87e5361f61af11d4b59495cd600a7f6f0d00c02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36472ce6a01f4a92b13e0a0d3c9676e69d824c762ea0fe835114f39102c641f1 0.600000000000 1887688 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": 1399393, "vin": [ { "gen": { "height": 1399383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36472ce6a01f4a92b13e0a0d3c9676e69d824c762ea0fe835114f39102c641f1" } } ], "extra": [ 1, 48, 1, 180, 250, 99, 197, 173, 238, 143, 185, 47, 97, 255, 168, 126, 83, 97, 246, 26, 241, 29, 75, 89, 73, 92, 214, 0, 167, 246, 240, 208, 12, 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