Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3aa4fe58282725aaeb082f6e571699b00b7f8aeae1943710f34b4d7bc40cc88

Tx prefix hash: 3404f55ca2e1f2deb44a65620686d27cf99e07e35029ef3a2838934bf0b5976d
Tx public key: 45207d7e18809dc179a921b1258818574bf5be5d94cdb5e0f4de1522394a0f5f
Timestamp: 1755190244 Timestamp [UCT]: 2025-08-14 16:50:44 Age [y:d:h:m:s]: 00:051:07:49:54
Block: 1346783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36166 RingCT/type: yes/0
Extra: 0145207d7e18809dc179a921b1258818574bf5be5d94cdb5e0f4de1522394a0f5f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aa33f6a939a340e6f03ec5765c4168449124e397d62cb0fbcafc3d64be3e045 0.600000000000 1834688 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": 1346793, "vin": [ { "gen": { "height": 1346783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aa33f6a939a340e6f03ec5765c4168449124e397d62cb0fbcafc3d64be3e045" } } ], "extra": [ 1, 69, 32, 125, 126, 24, 128, 157, 193, 121, 169, 33, 177, 37, 136, 24, 87, 75, 245, 190, 93, 148, 205, 181, 224, 244, 222, 21, 34, 57, 74, 15, 95, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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