Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00fd87fc8ec1caffc574ea7b43fe32e7f49ed9c8f958677a566cddd3e7d6b8e4

Tx prefix hash: 478e58fee3d15d2c08c55597f820d3f69146ec034d17bed98221cee76382ae6d
Tx public key: 3adae9400a449c2b8229ed8f9f8e3e6016f1b6df7311f86ad8bc8f153d9b789a
Timestamp: 1729792230 Timestamp [UCT]: 2024-10-24 17:50:30 Age [y:d:h:m:s]: 00:151:04:43:23
Block: 1138701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107851 RingCT/type: yes/0
Extra: 013adae9400a449c2b8229ed8f9f8e3e6016f1b6df7311f86ad8bc8f153d9b789a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a29918af63858942ec1fdc871c980f81444e4b62bd3a179e07f67f4d42ec4ec0 0.600000000000 1622406 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": 1138711, "vin": [ { "gen": { "height": 1138701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a29918af63858942ec1fdc871c980f81444e4b62bd3a179e07f67f4d42ec4ec0" } } ], "extra": [ 1, 58, 218, 233, 64, 10, 68, 156, 43, 130, 41, 237, 143, 159, 142, 62, 96, 22, 241, 182, 223, 115, 17, 248, 106, 216, 188, 143, 21, 61, 155, 120, 154, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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