Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80769f1e08085b447f62e37ad9186ad32b55935888ce4ed571111d2d2976c085

Tx prefix hash: d5002c7d2459a982f1d69a6bc1d1e3bb5029f909c986a13188c68511c9352a66
Tx public key: 47d0a1c39705e5430882ebcd619d8c34ea2cf1a820e38d8824a1c84b142f9c70
Timestamp: 1757630697 Timestamp [UCT]: 2025-09-11 22:44:57 Age [y:d:h:m:s]: 00:069:23:35:02
Block: 1366408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50121 RingCT/type: yes/0
Extra: 0147d0a1c39705e5430882ebcd619d8c34ea2cf1a820e38d8824a1c84b142f9c70021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1a2e67a7b647a7131ef24a62d636ea516ba53be20cada79ee3645ba98fd872 0.600000000000 1854447 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": 1366418, "vin": [ { "gen": { "height": 1366408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1a2e67a7b647a7131ef24a62d636ea516ba53be20cada79ee3645ba98fd872" } } ], "extra": [ 1, 71, 208, 161, 195, 151, 5, 229, 67, 8, 130, 235, 205, 97, 157, 140, 52, 234, 44, 241, 168, 32, 227, 141, 136, 36, 161, 200, 75, 20, 47, 156, 112, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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