Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66df9e913e0a0996d55ed572327931ff3932c4f30daf6eb2fcef99a37b5afe6c

Tx prefix hash: 56f6bc49f6ec2da2d53f3c3ab77308b8f11b58dacbb9c4b54025baf4e308064a
Tx public key: a504ece8cbc37667ac3295bff1e0ac5bb62417f0538c1043258c4d94b1955da9
Timestamp: 1750933004 Timestamp [UCT]: 2025-06-26 10:16:44 Age [y:d:h:m:s]: 00:141:10:23:39
Block: 1313122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99071 RingCT/type: yes/0
Extra: 01a504ece8cbc37667ac3295bff1e0ac5bb62417f0538c1043258c4d94b1955da90211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90b6883f0c86d30fa4b1abbd6b3b551944c6bceaa0c5d706ddd409da07a5dcd3 0.600000000000 1800759 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": 1313132, "vin": [ { "gen": { "height": 1313122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b6883f0c86d30fa4b1abbd6b3b551944c6bceaa0c5d706ddd409da07a5dcd3" } } ], "extra": [ 1, 165, 4, 236, 232, 203, 195, 118, 103, 172, 50, 149, 191, 241, 224, 172, 91, 182, 36, 23, 240, 83, 140, 16, 67, 37, 140, 77, 148, 177, 149, 93, 169, 2, 17, 0, 0, 0, 3, 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