Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5a254cfce9973a4516e038af578f79d785ac2ad0ef0d670632b5f4831296f1e

Tx prefix hash: 05428215767ff2f141e9242b61db1edb511b987f003b023f56a5dec09d2da36b
Tx public key: e36aef0855fc82f3439a5294806c5bd773d1c9321345cc6ed6afc98af0ff732f
Timestamp: 1694065494 Timestamp [UCT]: 2023-09-07 05:44:54 Age [y:d:h:m:s]: 01:272:21:38:16
Block: 842731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456190 RingCT/type: yes/0
Extra: 01e36aef0855fc82f3439a5294806c5bd773d1c9321345cc6ed6afc98af0ff732f02110000000833af99f4000000000000000000

1 output(s) for total of 0.990107682000 dcy

stealth address amount amount idx
00: 090d1de2a0848ead41a876c34323fd613a2cea260466a2c9ecc3f01ccdcf6cba 0.990107682000 1295881 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": 842741, "vin": [ { "gen": { "height": 842731 } } ], "vout": [ { "amount": 990107682, "target": { "key": "090d1de2a0848ead41a876c34323fd613a2cea260466a2c9ecc3f01ccdcf6cba" } } ], "extra": [ 1, 227, 106, 239, 8, 85, 252, 130, 243, 67, 154, 82, 148, 128, 108, 91, 215, 115, 209, 201, 50, 19, 69, 204, 110, 214, 175, 201, 138, 240, 255, 115, 47, 2, 17, 0, 0, 0, 8, 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