Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ad5c43d709ff0a3b58f270bd597488e09074847a9eef8fc7f1cf820e70a14dd

Tx prefix hash: 63335ab2d223ddc3cb1bf3cb5eeb0bd6dd537acae2f40a46366ccf1d2e00515b
Tx public key: afe7c517e0880099350edb7425fe2eb439a22a2b7fc49f11f44f73c9fbcd49f9
Timestamp: 1717375303 Timestamp [UCT]: 2024-06-03 00:41:43 Age [y:d:h:m:s]: 00:323:14:44:28
Block: 1035802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231283 RingCT/type: yes/0
Extra: 01afe7c517e0880099350edb7425fe2eb439a22a2b7fc49f11f44f73c9fbcd49f90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9484212ba047a88d1210dd45fd5a0c0b7c681881ce20ebf4d49a75ba45c20685 0.600000000000 1504325 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": 1035812, "vin": [ { "gen": { "height": 1035802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9484212ba047a88d1210dd45fd5a0c0b7c681881ce20ebf4d49a75ba45c20685" } } ], "extra": [ 1, 175, 231, 197, 23, 224, 136, 0, 153, 53, 14, 219, 116, 37, 254, 46, 180, 57, 162, 42, 43, 127, 196, 159, 17, 244, 79, 115, 201, 251, 205, 73, 249, 2, 17, 0, 0, 0, 2, 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