Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d5a2cd8ff8f7c8ee1f74249aaed8edf58f4279a99301e082c5c46a3fec836e5

Tx prefix hash: 68d2336b54bf5f1b31925e95b741ffeba0e5a02490c165ff7e2a51da6170b7b7
Tx public key: 641ec7dd00cd957ad9ba6d8fd28509a19d0f923d187ccff0ab38477107a765c8
Timestamp: 1718500378 Timestamp [UCT]: 2024-06-16 01:12:58 Age [y:d:h:m:s]: 00:194:17:27:49
Block: 1045137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139339 RingCT/type: yes/0
Extra: 01641ec7dd00cd957ad9ba6d8fd28509a19d0f923d187ccff0ab38477107a765c80211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e442b8daf7c067fbb1c8d8d145464d75cb28594fb71b2d60dbadebae0f9ac2a 0.600000000000 1514630 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": 1045147, "vin": [ { "gen": { "height": 1045137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e442b8daf7c067fbb1c8d8d145464d75cb28594fb71b2d60dbadebae0f9ac2a" } } ], "extra": [ 1, 100, 30, 199, 221, 0, 205, 149, 122, 217, 186, 109, 143, 210, 133, 9, 161, 157, 15, 146, 61, 24, 124, 207, 240, 171, 56, 71, 113, 7, 167, 101, 200, 2, 17, 0, 0, 0, 4, 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