Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 482dfda867cc0da83d50a3c3545831f801926ed58b0f3d6ff28eb4009604fa13

Tx prefix hash: b90015dcf66b0d9eacace3f4ff5c14c4d4e5d3067494e886a683c6f668d88c03
Tx public key: f943ab94a00950471876b791f4fd4fe9f9621bbe01e8295f9c71676dd3e583e9
Timestamp: 1706876091 Timestamp [UCT]: 2024-02-02 12:14:51 Age [y:d:h:m:s]: 00:286:13:03:38
Block: 948747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205163 RingCT/type: yes/0
Extra: 01f943ab94a00950471876b791f4fd4fe9f9621bbe01e8295f9c71676dd3e583e902110000000910a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f89c9e177521cbe5e0cb251ab28d303ed62fbb0bc8b2b88a889d1277528ac38e 0.600000000000 1407221 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": 948757, "vin": [ { "gen": { "height": 948747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f89c9e177521cbe5e0cb251ab28d303ed62fbb0bc8b2b88a889d1277528ac38e" } } ], "extra": [ 1, 249, 67, 171, 148, 160, 9, 80, 71, 24, 118, 183, 145, 244, 253, 79, 233, 249, 98, 27, 190, 1, 232, 41, 95, 156, 113, 103, 109, 211, 229, 131, 233, 2, 17, 0, 0, 0, 9, 16, 161, 116, 143, 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