Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94c9aaae80cf6f41dac295884dd6de9836d7f71e7e1304edf09d66d67dad358

Tx prefix hash: d60c4e6bc25051e4901ad1dca21e694ae4c102e892e51ed8b11a8b886c7be6e9
Tx public key: b7c7d4b3cd02831426f768d190db0ec27f6a6aeac44f5426d3d5618609806d3e
Timestamp: 1711402057 Timestamp [UCT]: 2024-03-25 21:27:37 Age [y:d:h:m:s]: 00:230:10:49:35
Block: 986296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164965 RingCT/type: yes/0
Extra: 01b7c7d4b3cd02831426f768d190db0ec27f6a6aeac44f5426d3d5618609806d3e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6955fec4a826c22b3cf6992d476102d5bd834a630bd19627133b1431f10d0703 0.600000000000 1446525 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": 986306, "vin": [ { "gen": { "height": 986296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6955fec4a826c22b3cf6992d476102d5bd834a630bd19627133b1431f10d0703" } } ], "extra": [ 1, 183, 199, 212, 179, 205, 2, 131, 20, 38, 247, 104, 209, 144, 219, 14, 194, 127, 106, 106, 234, 196, 79, 84, 38, 211, 213, 97, 134, 9, 128, 109, 62, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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