Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 106bb4b78e9a65549c6048511f8d02be32a678fb2fbc1c28b2fa0f3adb262523

Tx prefix hash: 735e3595a5ce1f6bcb999e0b229323bf6d462edf50c8aacfccd5f9a8d7beee5f
Tx public key: e7e43951e2bda1491f98ec6c9497ecd537c4cb2aac081d83d5ba96c1cd7922f9
Timestamp: 1699424994 Timestamp [UCT]: 2023-11-08 06:29:54 Age [y:d:h:m:s]: 02:000:19:41:38
Block: 886988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520350 RingCT/type: yes/0
Extra: 01e7e43951e2bda1491f98ec6c9497ecd537c4cb2aac081d83d5ba96c1cd7922f9021100000001679a8a81000000000000000000

1 output(s) for total of 0.706383510000 dcy

stealth address amount amount idx
00: 5a9ac1eb95c19732aa23390ba0e5d53a128168035be7cc59bb14b8e7af6d66ac 0.706383510000 1342837 of 0

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": 886998, "vin": [ { "gen": { "height": 886988 } } ], "vout": [ { "amount": 706383510, "target": { "key": "5a9ac1eb95c19732aa23390ba0e5d53a128168035be7cc59bb14b8e7af6d66ac" } } ], "extra": [ 1, 231, 228, 57, 81, 226, 189, 161, 73, 31, 152, 236, 108, 148, 151, 236, 213, 55, 196, 203, 42, 172, 8, 29, 131, 213, 186, 150, 193, 205, 121, 34, 249, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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