Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 106b687740190230c8c53858b196c34c26a53bafa4593c6aa69e370007f169ac

Tx prefix hash: 9aaa69218d3fb9b7c9df9339b4fcd98c8dec36064c94250b32aa3ca1f36e51df
Tx public key: 3cb850abccbbe4d5c111d0cf9e1e567ad0b6a1c3c6f23c6840f381437bcf664f
Timestamp: 1708917127 Timestamp [UCT]: 2024-02-26 03:12:07 Age [y:d:h:m:s]: 01:079:22:27:34
Block: 965672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318163 RingCT/type: yes/0
Extra: 013cb850abccbbe4d5c111d0cf9e1e567ad0b6a1c3c6f23c6840f381437bcf664f02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a641a7869ba5147e4865e5aa830e5965deda3c9e201a7e0e114ccc55b370af3 0.600000000000 1425427 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": 965682, "vin": [ { "gen": { "height": 965672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a641a7869ba5147e4865e5aa830e5965deda3c9e201a7e0e114ccc55b370af3" } } ], "extra": [ 1, 60, 184, 80, 171, 204, 187, 228, 213, 193, 17, 208, 207, 158, 30, 86, 122, 208, 182, 161, 195, 198, 242, 60, 104, 64, 243, 129, 67, 123, 207, 102, 79, 2, 17, 0, 0, 0, 7, 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