Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b548912ee3f01519120e40845704c83b06c1786b2cb3bc2746c8297d93e4fe

Tx prefix hash: 81f200ff8a0183d7d5ef6f5aa21968ed54a417fcdc1ee3a69d17c937d42d26ab
Tx public key: 536ad1f6f00f06d337eb1be5aca5f5df7bec69d5e81bd79238ffa0b09001b4e2
Timestamp: 1700368359 Timestamp [UCT]: 2023-11-19 04:32:39 Age [y:d:h:m:s]: 01:142:23:55:10
Block: 894795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363381 RingCT/type: yes/0
Extra: 01536ad1f6f00f06d337eb1be5aca5f5df7bec69d5e81bd79238ffa0b09001b4e202110000000233af99f4000000000000000000

1 output(s) for total of 0.665537773000 dcy

stealth address amount amount idx
00: 6c4f660acd4408b4a8b2fd3092f6731a5037bfbc118386756f7fde6443e845fa 0.665537773000 1351006 of 0

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": 894805, "vin": [ { "gen": { "height": 894795 } } ], "vout": [ { "amount": 665537773, "target": { "key": "6c4f660acd4408b4a8b2fd3092f6731a5037bfbc118386756f7fde6443e845fa" } } ], "extra": [ 1, 83, 106, 209, 246, 240, 15, 6, 211, 55, 235, 27, 229, 172, 165, 245, 223, 123, 236, 105, 213, 232, 27, 215, 146, 56, 255, 160, 176, 144, 1, 180, 226, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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