Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efc122dc94d5b3f8dbd2de9d6985b1028a73aa696efe23c320c57127e67ef170

Tx prefix hash: f1ea9c9ec8adafcdb71218c889c868edbf58c3e33cff487bbf0ec6f3c3fc015a
Tx public key: dcc2c90ba80cbe66ac0138caef016e9b79dbb808e1cc22b34f25609021536774
Timestamp: 1698241354 Timestamp [UCT]: 2023-10-25 13:42:34 Age [y:d:h:m:s]: 01:089:21:57:25
Block: 877383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325440 RingCT/type: yes/0
Extra: 01dcc2c90ba80cbe66ac0138caef016e9b79dbb808e1cc22b34f2560902153677402110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.760091575000 dcy

stealth address amount amount idx
00: 4c4bef623c9b0d354a8f4f45537ee7bc65e1a2f538e82c053f72ae902da9555c 0.760091575000 1332757 of 0

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": 877393, "vin": [ { "gen": { "height": 877383 } } ], "vout": [ { "amount": 760091575, "target": { "key": "4c4bef623c9b0d354a8f4f45537ee7bc65e1a2f538e82c053f72ae902da9555c" } } ], "extra": [ 1, 220, 194, 201, 11, 168, 12, 190, 102, 172, 1, 56, 202, 239, 1, 110, 155, 121, 219, 184, 8, 225, 204, 34, 179, 79, 37, 96, 144, 33, 83, 103, 116, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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