Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc510aa1ba27abd2bbdf579fc312ab2d01c236aef05b1a703dad77707f6841d

Tx prefix hash: 49c4b91d9de42e467ac2b832ab5422664f9eb65797d7f2aa1bcae9eb7a6558d7
Tx public key: 7510727d66bb17d0ced7f58c67a60f56ca7e49796fcc84ca8d3002ddce3bc57f
Timestamp: 1685505092 Timestamp [UCT]: 2023-05-31 03:51:32 Age [y:d:h:m:s]: 01:226:13:54:43
Block: 771828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423351 RingCT/type: yes/0
Extra: 017510727d66bb17d0ced7f58c67a60f56ca7e49796fcc84ca8d3002ddce3bc57f02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.700644763000 dcy

stealth address amount amount idx
00: 9272935c7a337105d4d0e09d3ab4780d1ce97cc9c60e57d88935d5eb21c84a5b 1.700644763000 1221207 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": 771838, "vin": [ { "gen": { "height": 771828 } } ], "vout": [ { "amount": 1700644763, "target": { "key": "9272935c7a337105d4d0e09d3ab4780d1ce97cc9c60e57d88935d5eb21c84a5b" } } ], "extra": [ 1, 117, 16, 114, 125, 102, 187, 23, 208, 206, 215, 245, 140, 103, 166, 15, 86, 202, 126, 73, 121, 111, 204, 132, 202, 141, 48, 2, 221, 206, 59, 197, 127, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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