Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a165845dcf2959c3206c947c1d9dd2f6433b6cbc90f9afdbbc6f94a6940995c

Tx prefix hash: 2b230a4d9c7cb649ea7f6864bc34b5a6abc7ff73739161ad6a8385da3813d7fe
Tx public key: 59e8c1479a8d74ab1dce1c3dc8a1d4946a48a6f4ff377b8bd64d742c3aa9ef5e
Timestamp: 1705974872 Timestamp [UCT]: 2024-01-23 01:54:32 Age [y:d:h:m:s]: 01:084:23:39:51
Block: 941244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321856 RingCT/type: yes/0
Extra: 0159e8c1479a8d74ab1dce1c3dc8a1d4946a48a6f4ff377b8bd64d742c3aa9ef5e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2c8a95835967cd2c06fc6aa77e688edb9ad190beaa94cbc80bbd6c4a2695ba9 0.600000000000 1399390 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": 941254, "vin": [ { "gen": { "height": 941244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2c8a95835967cd2c06fc6aa77e688edb9ad190beaa94cbc80bbd6c4a2695ba9" } } ], "extra": [ 1, 89, 232, 193, 71, 154, 141, 116, 171, 29, 206, 28, 61, 200, 161, 212, 148, 106, 72, 166, 244, 255, 55, 123, 139, 214, 77, 116, 44, 58, 169, 239, 94, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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