Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a981f2ad42b424c0ebad3b70492b52b1cbc00fd65a1c9be0345c7d4b3d1f4f69

Tx prefix hash: db70fbaf5d04fb1799a132eef32e5d8f101cd7282c37861e0192266968bdb032
Tx public key: d925e21421707b07924c43352cec59a5c022de5ca1ff515c6e465fcf1c5080e9
Timestamp: 1590432270 Timestamp [UCT]: 2020-05-25 18:44:30 Age [y:d:h:m:s]: 04:253:06:07:38
Block: 103219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106930 RingCT/type: yes/0
Extra: 01d925e21421707b07924c43352cec59a5c022de5ca1ff515c6e465fcf1c5080e9021100000197d8e16910000000000000000000

1 output(s) for total of 279.250116346000 dcy

stealth address amount amount idx
00: f4ac41d05e2d0ebc0acc320a323acbadff7f4a1ec493b62cf5511badb90e23d9 279.250116346000 181108 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": 103229, "vin": [ { "gen": { "height": 103219 } } ], "vout": [ { "amount": 279250116346, "target": { "key": "f4ac41d05e2d0ebc0acc320a323acbadff7f4a1ec493b62cf5511badb90e23d9" } } ], "extra": [ 1, 217, 37, 226, 20, 33, 112, 123, 7, 146, 76, 67, 53, 44, 236, 89, 165, 192, 34, 222, 92, 161, 255, 81, 92, 110, 70, 95, 207, 28, 80, 128, 233, 2, 17, 0, 0, 1, 151, 216, 225, 105, 16, 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