Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d2ba2bf080c732c90b43131c4e39e6b1f3556f325b5a006612828ae6383e72

Tx prefix hash: 43a996118d46c5b654bdc8beac198307b3a83cb28611772c1efba4da02ec8db8
Tx public key: 022758047444e2a762459b16461c6c1e2f0933f6bb29c65900f3f18e2475cca2
Timestamp: 1751640583 Timestamp [UCT]: 2025-07-04 14:49:43 Age [y:d:h:m:s]: 00:137:23:18:50
Block: 1318668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96902 RingCT/type: yes/0
Extra: 01022758047444e2a762459b16461c6c1e2f0933f6bb29c65900f3f18e2475cca2021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f599c068c95b9bc7e4bab605990a5f672a6e50433e9d4f1eba82923b1148a6a5 0.600000000000 1806353 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": 1318678, "vin": [ { "gen": { "height": 1318668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f599c068c95b9bc7e4bab605990a5f672a6e50433e9d4f1eba82923b1148a6a5" } } ], "extra": [ 1, 2, 39, 88, 4, 116, 68, 226, 167, 98, 69, 155, 22, 70, 28, 108, 30, 47, 9, 51, 246, 187, 41, 198, 89, 0, 243, 241, 142, 36, 117, 204, 162, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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