Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2af0c71656c5879f25966f5ced22966133a2b2e7cbe11f3ee5af25e4206cd7f

Tx prefix hash: 0d6416f44cfa0b6e2ea09f360ee9bbc4b65c7867d1eb392b6ccfaa94acb7b8a2
Tx public key: 63b5e166779c7cc00e1af084bf95c2f67c30ab9a1946a782d9e6204e60eb003c
Timestamp: 1715222157 Timestamp [UCT]: 2024-05-09 02:35:57 Age [y:d:h:m:s]: 01:184:01:17:10
Block: 1017952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390155 RingCT/type: yes/0
Extra: 0163b5e166779c7cc00e1af084bf95c2f67c30ab9a1946a782d9e6204e60eb003c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5745896e9a097e3a135798e1b4174c7af7ce28e329f234a734202f14907e1a87 0.600000000000 1481737 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": 1017962, "vin": [ { "gen": { "height": 1017952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5745896e9a097e3a135798e1b4174c7af7ce28e329f234a734202f14907e1a87" } } ], "extra": [ 1, 99, 181, 225, 102, 119, 156, 124, 192, 14, 26, 240, 132, 191, 149, 194, 246, 124, 48, 171, 154, 25, 70, 167, 130, 217, 230, 32, 78, 96, 235, 0, 60, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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