Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2c8842fb330dbd57f6ecf0f1dfd1d1dff8b42f3527726e1307d847b0efb7159

Tx prefix hash: 1c2fe94534d8c41cf9222f6832604c4b985eca4e931409e2020dba6b5009aa8b
Tx public key: 1c00adb3cc29df5c1bd015754ed969a9808bb94c477f285082fe1d6239f15cd2
Timestamp: 1715367681 Timestamp [UCT]: 2024-05-10 19:01:21 Age [y:d:h:m:s]: 00:203:03:31:36
Block: 1019168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145398 RingCT/type: yes/0
Extra: 011c00adb3cc29df5c1bd015754ed969a9808bb94c477f285082fe1d6239f15cd20211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ab00e72426de0e5f02fc909f9eb2cf7ad7eca0cb2a52171dc6d5e3600d7dad7 0.600000000000 1483065 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": 1019178, "vin": [ { "gen": { "height": 1019168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ab00e72426de0e5f02fc909f9eb2cf7ad7eca0cb2a52171dc6d5e3600d7dad7" } } ], "extra": [ 1, 28, 0, 173, 179, 204, 41, 223, 92, 27, 208, 21, 117, 78, 217, 105, 169, 128, 139, 185, 76, 71, 127, 40, 80, 130, 254, 29, 98, 57, 241, 92, 210, 2, 17, 0, 0, 0, 2, 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