Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c6ffb9f4750d0d183b9f12fe223b2e498cecc2475df47923d2ca1aab733af99

Tx prefix hash: e1ebe4351b7d726e6e4fd7c09c673dc116b3985f99596aa8222a8bd7f7ef8152
Tx public key: 9d8605dc22cd55a052e3f0bfd9aeb3c329fb3d217e9db0706c78f218a716b106
Timestamp: 1723617726 Timestamp [UCT]: 2024-08-14 06:42:06 Age [y:d:h:m:s]: 00:233:04:40:03
Block: 1087556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166532 RingCT/type: yes/0
Extra: 019d8605dc22cd55a052e3f0bfd9aeb3c329fb3d217e9db0706c78f218a716b106021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf1b09a7967f4d6053ae0fa90421424314adcacdfd33f4cd935e722edcd4763 0.600000000000 1562165 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": 1087566, "vin": [ { "gen": { "height": 1087556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf1b09a7967f4d6053ae0fa90421424314adcacdfd33f4cd935e722edcd4763" } } ], "extra": [ 1, 157, 134, 5, 220, 34, 205, 85, 160, 82, 227, 240, 191, 217, 174, 179, 195, 41, 251, 61, 33, 126, 157, 176, 112, 108, 120, 242, 24, 167, 22, 177, 6, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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