Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebf669fdaafe2afa7cefee37a46a682b792b27b3a5521ce83ecd98d810222c36

Tx prefix hash: 90e206415ac571cc98f2a7d78dc833b3420a5a9d2de0abe7e2238cf5d111b6c5
Tx public key: e04e8a7b0af2dce8bcf3c1ce8220cffebdcdcf958b82ed2aafcc1134d97c912a
Timestamp: 1761756116 Timestamp [UCT]: 2025-10-29 16:41:56 Age [y:d:h:m:s]: 00:022:05:46:03
Block: 1400625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15905 RingCT/type: yes/0
Extra: 01e04e8a7b0af2dce8bcf3c1ce8220cffebdcdcf958b82ed2aafcc1134d97c912a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fca8416afbbb4af36ffd99831bca0fcd5f0e019249a986112e727d075ff536d3 0.600000000000 1888942 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": 1400635, "vin": [ { "gen": { "height": 1400625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fca8416afbbb4af36ffd99831bca0fcd5f0e019249a986112e727d075ff536d3" } } ], "extra": [ 1, 224, 78, 138, 123, 10, 242, 220, 232, 188, 243, 193, 206, 130, 32, 207, 254, 189, 205, 207, 149, 139, 130, 237, 42, 175, 204, 17, 52, 217, 124, 145, 42, 2, 17, 0, 0, 0, 1, 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