Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7402a761d224d11049373332fbafc0c3a9ac82f41e9c41e9b79d320c76edbb4

Tx prefix hash: 8091220cca400824cba6e8aac0ca3dfa3fd2653613223625a8f40e6c9911ba4f
Tx public key: 08b69b0f27fa26330d643358eae883d49af63f41074ed8a53a8d044f78625f57
Timestamp: 1753433501 Timestamp [UCT]: 2025-07-25 08:51:41 Age [y:d:h:m:s]: 00:191:01:56:28
Block: 1332969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135305 RingCT/type: yes/0
Extra: 0108b69b0f27fa26330d643358eae883d49af63f41074ed8a53a8d044f78625f5702110000000bef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d365b200a95e8067bfb30a0bc306f6fd149ea582a0669e4b5cdf87197cc31f8 0.600000000000 1820768 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": 1332979, "vin": [ { "gen": { "height": 1332969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d365b200a95e8067bfb30a0bc306f6fd149ea582a0669e4b5cdf87197cc31f8" } } ], "extra": [ 1, 8, 182, 155, 15, 39, 250, 38, 51, 13, 100, 51, 88, 234, 232, 131, 212, 154, 246, 63, 65, 7, 78, 216, 165, 58, 141, 4, 79, 120, 98, 95, 87, 2, 17, 0, 0, 0, 11, 239, 34, 20, 133, 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