Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bf44c1b8f243e91679c2e0621c7a1c0e445b047357de22c9ff9fe1cea3730d5

Tx prefix hash: a3bd39abb495cbfbb8eb28eb7a192857c7cc1cf7eec176ede0fba46d96a30695
Tx public key: 16895ddea6f066f7dca67394e4362b826cf5392be9d60e106c77080dcdebfb30
Timestamp: 1719687983 Timestamp [UCT]: 2024-06-29 19:06:23 Age [y:d:h:m:s]: 01:130:19:54:43
Block: 1054965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352044 RingCT/type: yes/0
Extra: 0116895ddea6f066f7dca67394e4362b826cf5392be9d60e106c77080dcdebfb300211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 661f1f166efe737364fdf8a9fb8aa4666d4b8472b90d69f306493ff8d76fb1b6 0.600000000000 1525356 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": 1054975, "vin": [ { "gen": { "height": 1054965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "661f1f166efe737364fdf8a9fb8aa4666d4b8472b90d69f306493ff8d76fb1b6" } } ], "extra": [ 1, 22, 137, 93, 222, 166, 240, 102, 247, 220, 166, 115, 148, 228, 54, 43, 130, 108, 245, 57, 43, 233, 214, 14, 16, 108, 119, 8, 13, 205, 235, 251, 48, 2, 17, 0, 0, 0, 2, 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