Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1da7cbafd458a13f680507fb4c9cde3583770497dba82cabe4439720ea91294

Tx prefix hash: 0d759ffc5a6a76d3284a85da6f3a8c5bdf181d57f2a4a8f49769daf8037ed854
Tx public key: f4ae2bc18a4156eaf33b7b43c800ca97aaff7551afdafdcf9e0ccacd29e5b44f
Timestamp: 1707861260 Timestamp [UCT]: 2024-02-13 21:54:20 Age [y:d:h:m:s]: 01:053:06:44:50
Block: 956921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299102 RingCT/type: yes/0
Extra: 01f4ae2bc18a4156eaf33b7b43c800ca97aaff7551afdafdcf9e0ccacd29e5b44f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f777baa88f0fbd41236784640a4400e14aabb5fb27b1aa40d3c9888a80870e65 0.600000000000 1416233 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": 956931, "vin": [ { "gen": { "height": 956921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f777baa88f0fbd41236784640a4400e14aabb5fb27b1aa40d3c9888a80870e65" } } ], "extra": [ 1, 244, 174, 43, 193, 138, 65, 86, 234, 243, 59, 123, 67, 200, 0, 202, 151, 170, 255, 117, 81, 175, 218, 253, 207, 158, 12, 202, 205, 41, 229, 180, 79, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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