Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416904bf89687ec6f291614afd4354c8b716231ab46b4f05ac3bf03cbc1f4c2e

Tx prefix hash: a93614c988faeea79912b8a5090958ab7f71d6e0d5f1520548dd3dfa59f93c5d
Tx public key: bf7279ba08e5a5420c7daffd0db63fd5675d0d660580266a3aba257543e63c64
Timestamp: 1720101368 Timestamp [UCT]: 2024-07-04 13:56:08 Age [y:d:h:m:s]: 00:271:00:31:30
Block: 1058389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193639 RingCT/type: yes/0
Extra: 01bf7279ba08e5a5420c7daffd0db63fd5675d0d660580266a3aba257543e63c6402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4afed85b25d3afaa1da02be8a8d83c158d2395581e99f193a98ac9f70b7e9b1 0.600000000000 1528844 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": 1058399, "vin": [ { "gen": { "height": 1058389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4afed85b25d3afaa1da02be8a8d83c158d2395581e99f193a98ac9f70b7e9b1" } } ], "extra": [ 1, 191, 114, 121, 186, 8, 229, 165, 66, 12, 125, 175, 253, 13, 182, 63, 213, 103, 93, 13, 102, 5, 128, 38, 106, 58, 186, 37, 117, 67, 230, 60, 100, 2, 17, 0, 0, 0, 1, 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