Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42fe1e4c038cacd46aaa9057f50a8cfcf7b4280a7b643e22df0336ed445ff461

Tx prefix hash: 867af885c6cc1a7e6481605d333e4999f3c8258b579baa2c9fed29070c7f8642
Tx public key: edb275976958c28fd6a678ec44cd13fdf252e9a6acb9c7a02a4c689a547ab8ed
Timestamp: 1724525374 Timestamp [UCT]: 2024-08-24 18:49:34 Age [y:d:h:m:s]: 00:295:15:07:03
Block: 1095096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211065 RingCT/type: yes/0
Extra: 01edb275976958c28fd6a678ec44cd13fdf252e9a6acb9c7a02a4c689a547ab8ed02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e3aa21239b5dd4469825ad4e465c9061dbb11a1cd1fb256f02b3bb44136f76d 0.600000000000 1570237 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": 1095106, "vin": [ { "gen": { "height": 1095096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e3aa21239b5dd4469825ad4e465c9061dbb11a1cd1fb256f02b3bb44136f76d" } } ], "extra": [ 1, 237, 178, 117, 151, 105, 88, 194, 143, 214, 166, 120, 236, 68, 205, 19, 253, 242, 82, 233, 166, 172, 185, 199, 160, 42, 76, 104, 154, 84, 122, 184, 237, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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