Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6343a8e2a58c1b4161a458997dab45add21a74fca08469a2d0c2187b90b33ac4

Tx prefix hash: 008ca710e9dd20a602db74af8be969c2097698e274855c8a64c136ac6b3b07ea
Tx public key: fbc35c89013b0f318690fa49c07721fdea002f568c1f1d99f0c9fd3f8845c053
Timestamp: 1721872088 Timestamp [UCT]: 2024-07-25 01:48:08 Age [y:d:h:m:s]: 00:275:17:29:36
Block: 1073075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196998 RingCT/type: yes/0
Extra: 01fbc35c89013b0f318690fa49c07721fdea002f568c1f1d99f0c9fd3f8845c05302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5686d31368bc597ca1b6836e6e3757cb87d3cf71956e72d721bdc14bf918c568 0.600000000000 1545574 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": 1073085, "vin": [ { "gen": { "height": 1073075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5686d31368bc597ca1b6836e6e3757cb87d3cf71956e72d721bdc14bf918c568" } } ], "extra": [ 1, 251, 195, 92, 137, 1, 59, 15, 49, 134, 144, 250, 73, 192, 119, 33, 253, 234, 0, 47, 86, 140, 31, 29, 153, 240, 201, 253, 63, 136, 69, 192, 83, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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