Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f9f6c3212d01a302b1d6574aab8a30d15605933b579406d656680fd464bd80

Tx prefix hash: 5b494ce420166523150d4cc70bbc3c91c6e6685c50d2cbbd38bfef7f2ffe8592
Tx public key: 4791a5f6461d6ab0f895c30df8f61f77eb472c069cb41dc3474a9910bf9877f7
Timestamp: 1704787705 Timestamp [UCT]: 2024-01-09 08:08:25 Age [y:d:h:m:s]: 01:330:06:58:01
Block: 931416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494946 RingCT/type: yes/0
Extra: 014791a5f6461d6ab0f895c30df8f61f77eb472c069cb41dc3474a9910bf9877f702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5b3ac6b4bbccadd89bb1e7d4c18f1b21214086f967d66899705d758e7a6e8c 0.600000000000 1389314 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": 931426, "vin": [ { "gen": { "height": 931416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5b3ac6b4bbccadd89bb1e7d4c18f1b21214086f967d66899705d758e7a6e8c" } } ], "extra": [ 1, 71, 145, 165, 246, 70, 29, 106, 176, 248, 149, 195, 13, 248, 246, 31, 119, 235, 71, 44, 6, 156, 180, 29, 195, 71, 74, 153, 16, 191, 152, 119, 247, 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