Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8c6047178cdbbdd42d769a9fcaceef8b51ef948c32bf5527c09f3b12f5592ed

Tx prefix hash: efa018673a8a4994f68e1d6bfc3bffdbefc3fe6c30fb0f51c818228c1870e325
Tx public key: 329c34259f3253c4989e13997d672f7f1f8d16250a74d9665b10dbabb4e5e991
Timestamp: 1707598491 Timestamp [UCT]: 2024-02-10 20:54:51 Age [y:d:h:m:s]: 00:360:23:18:24
Block: 954731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258130 RingCT/type: yes/0
Extra: 01329c34259f3253c4989e13997d672f7f1f8d16250a74d9665b10dbabb4e5e9910211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2e312e2b424578b7d7f41d34bdfabb2049d96d42d129c9f85eca4d6c4b019a 0.600000000000 1414013 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": 954741, "vin": [ { "gen": { "height": 954731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2e312e2b424578b7d7f41d34bdfabb2049d96d42d129c9f85eca4d6c4b019a" } } ], "extra": [ 1, 50, 156, 52, 37, 159, 50, 83, 196, 152, 158, 19, 153, 125, 103, 47, 127, 31, 141, 22, 37, 10, 116, 217, 102, 91, 16, 219, 171, 180, 229, 233, 145, 2, 17, 0, 0, 0, 7, 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