Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340af15a7737a079d0623e7db8a99323bd38f3568062ab2db7d25ab23af1b2b1

Tx prefix hash: 54860efbc2ef98df2c81ef5ca8acbee4e7997bb92e463157f804f9d832bb3f32
Tx public key: e0e6bc5a2ca163e1cafee638f8e3b9694ec939d00203c1757b8eb72cdceb9209
Timestamp: 1702895814 Timestamp [UCT]: 2023-12-18 10:36:54 Age [y:d:h:m:s]: 01:149:13:59:17
Block: 915752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368061 RingCT/type: yes/0
Extra: 01e0e6bc5a2ca163e1cafee638f8e3b9694ec939d00203c1757b8eb72cdceb920902110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50ed97494f2715638c2960eb324d792e6e2acfe1ac3410c6063beb2e1b5f1af7 0.600000000000 1373176 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": 915762, "vin": [ { "gen": { "height": 915752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50ed97494f2715638c2960eb324d792e6e2acfe1ac3410c6063beb2e1b5f1af7" } } ], "extra": [ 1, 224, 230, 188, 90, 44, 161, 99, 225, 202, 254, 230, 56, 248, 227, 185, 105, 78, 201, 57, 208, 2, 3, 193, 117, 123, 142, 183, 44, 220, 235, 146, 9, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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