Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b5dbbb14cfbc3e97fe6463910e96bde66050a8ebe2d5821fb3c4deec1ea5ec6

Tx prefix hash: d5dda9cfa8e7d6659c7a50a13eaf7986c3b77933dbdaf154dc0577f31deb0528
Tx public key: ca6d55f3429d4c508b267b1b4b810ec393f296fa6add32be11b42a0c05492b04
Timestamp: 1750008502 Timestamp [UCT]: 2025-06-15 17:28:22 Age [y:d:h:m:s]: 00:159:06:33:30
Block: 1305681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111613 RingCT/type: yes/0
Extra: 01ca6d55f3429d4c508b267b1b4b810ec393f296fa6add32be11b42a0c05492b0402110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542cdd7498a3908c45cb943df88c68adc0807469fdaf2515fdc9b5f90fed37ab 0.600000000000 1793282 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": 1305691, "vin": [ { "gen": { "height": 1305681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542cdd7498a3908c45cb943df88c68adc0807469fdaf2515fdc9b5f90fed37ab" } } ], "extra": [ 1, 202, 109, 85, 243, 66, 157, 76, 80, 139, 38, 123, 27, 75, 129, 14, 195, 147, 242, 150, 250, 106, 221, 50, 190, 17, 180, 42, 12, 5, 73, 43, 4, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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