Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d71003c07d52746de83cbc3a55e1d9d67ab4fefb171335cde03fdc902ac9210f

Tx prefix hash: 0c4da3bace3a056c97a8f2cd6c696245181c0f150cf6f9e519539cba4e877c2d
Tx public key: 1e15dd76db37a4ad67f0a3d0884c543827e27211c110312682c1ed7ca3b01747
Timestamp: 1718300883 Timestamp [UCT]: 2024-06-13 17:48:03 Age [y:d:h:m:s]: 00:224:13:02:08
Block: 1043469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160647 RingCT/type: yes/0
Extra: 011e15dd76db37a4ad67f0a3d0884c543827e27211c110312682c1ed7ca3b017470211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70286eb9eb45a179493e098aca050fc7075a5534a8bf0cb24bf78638511c24a0 0.600000000000 1512622 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": 1043479, "vin": [ { "gen": { "height": 1043469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70286eb9eb45a179493e098aca050fc7075a5534a8bf0cb24bf78638511c24a0" } } ], "extra": [ 1, 30, 21, 221, 118, 219, 55, 164, 173, 103, 240, 163, 208, 136, 76, 84, 56, 39, 226, 114, 17, 193, 16, 49, 38, 130, 193, 237, 124, 163, 176, 23, 71, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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